auto release on vnext #5426
Merged
auto release on vnext #5426
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🦋 Changeset detectedLatest commit: 176f5c6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 7 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
kanej
force-pushed
the
chore/auto-release-on-vnext
branch
from
3472f03 to
93fa627
Compare
kanej
force-pushed
the
chore/auto-release-on-vnext
branch
from
93fa627 to
ee582c6
Compare
kanej
force-pushed
the
chore/auto-release-on-vnext
branch
from
ee582c6 to
7e1f3ec
Compare
kanej
commented
Jun 24, 2024
| run: echo "//registry.npmjs.org/:_authToken=${{ secrets.VNEXT_NPM_TOKEN }}" > .npmrc | ||
| - name: Publish | ||
| if: needs.changesetcheck.outputs.CHANGESETS == 'found' | ||
| run: pnpm publish -r --no-git-checks --tag next --access public --dry-run |
kanej
commented
Jun 24, 2024
| if: needs.changesetcheck.outputs.CHANGESETS == 'found' | ||
| run: pnpm publish -r --no-git-checks --tag next --access public --dry-run | ||
| env: | ||
| NPM_CONFIG_PROVENANCE: true |
There was a problem hiding this comment.
This gets us the provenance tag on npmjs.com
kanej
force-pushed
the
chore/auto-release-on-vnext
branch
from
a47d5cd to
b9e9d4f
Compare
kanej
force-pushed
the
chore/auto-release-on-vnext
branch
from
b9e9d4f to
a9b84ec
Compare
kanej
force-pushed
the
chore/auto-release-on-vnext
branch
from
a9b84ec to
73612dc
Compare
In prep for auto-releasing from v-next, switch the v-next packages to be named under the `@ignored` org. Set the versions to `v2.0.0` in prep for manual release.
Taking the `@ignored` changes and applying them across imports and things like the test commands.
Apply the prerelease config based on a flag of `next`.
kanej
force-pushed
the
chore/auto-release-on-vnext
branch
from
2747c0d to
0cb9e6b
Compare
kanej
force-pushed
the
chore/auto-release-on-vnext
branch
from
0cb9e6b to
9cac542
Compare
kanej
force-pushed
the
chore/auto-release-on-vnext
branch
from
9cac542 to
b49e663
Compare
kanej
force-pushed
the
chore/auto-release-on-vnext
branch
from
999caba to
2606d81
Compare
kanej
force-pushed
the
chore/auto-release-on-vnext
branch
from
2606d81 to
84da594
Compare
There are 3 moves here: - Remove the pushing of tags - Move the if check to the job level rather than per step - temporarily comment out the git push
kanej
force-pushed
the
chore/auto-release-on-vnext
branch
from
84da594 to
2eab529
Compare
kanej
force-pushed
the
chore/auto-release-on-vnext
branch
from
2eab529 to
a6395a1
Compare
kanej
force-pushed
the
chore/auto-release-on-vnext
branch
from
a6395a1 to
a5a5a08
Compare
alcuadrado
approved these changes
Jun 27, 2024
kanej
force-pushed
the
chore/auto-release-on-vnext
branch
from
a5a5a08 to
176f5c6
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Setup auto deployment of
v-nextpackages.Approach
v-nextpackages to be under the@ignoredorg in npm@nomicfoundation/hardhat-core->@ignored/hardhat-vnext-core@nomicfoundation/hardhat-build-system->@ignored/hardhat-vnext-build-system@nomicfoundation/hardhat-errors->@ignored/hardhat-vnext-errors@nomicfoundation/hardhat-node-test-reporter->@ignored/hardhat-vnext-node-test-reporter@nomicfoundation/hardhat-utils->@ignored/hardhat-vnext-utils@nomicfoundation/hardhat-zod-utils->@ignored/hardhat-vnext-zod-utils@nomicfoundation/hardhat->@ignored/hardhat-vnext2.0.0for each of these packages manuallyVNEXT_NPM_TOKENthat is limited to thev-nextpackagesv-next-changesets-release.ymlleveraging theVNEXT_NPM_TOKENv-nextpackage that has a major update to3.0.0-next.0prereleasev-nextthis PR should publish pre-release versions of eachv-nextpackage under safe@ignoredvariants.